Fix NativeMarshalling attribute override for COM interfaces #121643
+44
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
[NativeMarshalling(typeof(CustomMarshaller<T>))]attribute on COM interfaces was ignored, always using the defaultComInterfaceMarshaller<T>instead.Changes
ComInterfaceMarshallingInfoProvider.cs: Return
nullwhenNativeMarshallingAttributeis present, allowing the parser chain to reachNativeMarshallingAttributeParserwhich handles the custom marshaller.Tests: Added validation for both COM interface method parameters and LibraryImport usage.
This allows consumers to specify custom marshallers (e.g.,
UniqueComInterfaceMarshaller<T>for unique RCW instances) via the standardNativeMarshallingAttributemechanism.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.